…ntract addresses (#29573)

## **Description**

Updates the Polymarket adapter contract addresses used by Predict to the
new `CtfCollateralAdapter` and `NegRiskCtfCollateralAdapter` values
shared by Polymarket.

Polymarket added new events on these adapters and will stop accepting
relayed transactions through the old adapters on May 1 at 3pm UTC.
Without this change, Polymarket transactions routed through the old
adapters will start failing.

## **Changelog**

CHANGELOG entry: Updated Polymarket adapter contracts so Polymarket
prediction transactions continue working after the relayer migration.

## **Related issues**

Fixes:
- PRED-853
- https://consensyssoftware.atlassian.net/browse/PRED-853

## **Manual testing steps**

```gherkin
Feature: Polymarket adapter migration

  Scenario: user submits a Polymarket transaction after the adapter migration
    Given the app is running a build from this branch
    And the user has access to the Predict/Polymarket experience

    When the user submits a Polymarket transaction that uses the collateral adapters
    Then the app should use the updated adapter addresses
    And the transaction should be accepted by the relayer after the migration cutoff
```

Not run locally; constants-only configuration update.

## **Screenshots/Recordings**

Not applicable.

### **Before**

Not applicable.

### **After**

Not applicable.

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [ ] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [ ] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [ ] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Low code complexity, but changes production on-chain contract targets
for Polymarket claim/relay flows; incorrect addresses would cause
transactions to fail.
> 
> **Overview**
> Updates Predict’s Polymarket configuration to use new
`CtfCollateralAdapter` and `NegRiskCtfCollateralAdapter` contract
addresses in `polymarket/constants.ts`.
> 
> This shifts v2 claim/relay routing (as referenced by protocol
`claim.standardTarget`/`claim.negRiskTarget`) to the new adapter
contracts to maintain compatibility with Polymarket’s relayer migration.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
08b08be. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->